View CY7C68300C-56LTXC_4799629.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c ez-usb at2lp? usb 2.0 to ata/atapi bridge cypress semiconductor corporation ? 198 champion court ? san jose , ca 95134-1709 ? 408-943-2600 document number: 001-05809 rev. *h revised january 3, 2011 ez-usb at2lp? usb 2.0 to ata/atapi bridge features fixed function mass storage device - requires no firmware two power modes: self powered and usb bus powered to enable bus powered cf (compactflash) readers and truly portable usb hard drives certified compliant for usb 2.0 (tid# 40490119), the usb mass storage class, and the usb mass storage class bulk-only transport (bot) specification operates at high-speed (480 mbps) or full-speed (12 mbps) usb complies with ata/atapi-6 specification supports 48-bit addressing for large hard drives supports ata security features supports any ata command with the atacb function supports mode for bios boot support supports atapi serial number vpd page retrieval for digital rights management (drm) compatibility supports pio modes 0, 3, and 4, multiword dma mode 2, and udma modes 2, 3, and 4 uses one small external seri al eeprom for storage of usb descriptors and device configuration data ata interface irq signal support supports one or two ata/atapi devices supports compactflash and one ata/atapi device supports board-level manufacturing test using the usb i/f places the ata interface in high impedance (high z) to enable sharing of the ata bus with another controller such as an ieee-1394 to ata bridge chip or mp3 decoder) low power 3.3 v operation fully compatible with native usb mass storage class drivers cypress mass storage class drivers available for windows ? (98se, me, 2000, xp) and mac os x operating systems features (cy7c68320c/cy7c68321c only) supports hid interface or cust om gpios to enable features such as single button backu p, power off, and led-based notification 56-pin qfn and 100-pin tqfp pb-free packages cy7c68321c is ideal for battery powered designs cy7c68320c is ideal for self and bus powered designs automotive aec grade option (?40 c to 85 c) features (cy7c68300c/cy7c68301c only) pin compatible with cy7c68300a (using backward compatibility mode) 56-pin ssop and 56-pin qfn pb-free packages cy7c68301c is ideal for battery powered designs cy7c68300c is ideal for self and bus powered designs [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 2 of 44 applications the cy7c68300c/301c and cy7c68320c/321a implement a usb 2.0 bridge for all ata/atapi-6 compliant mass storage devices, such as the following: hard drives cd-rom, cd-r/w dvd-rom, dvd-ram, dvdr/w mp3 players personal media players compactflash microdrives tape drives personal video recorders automotive applications the cy7c68300c/301c and cy7c68320c/321a support one or two devices in the following configurations: ata/atapi master only ata/atapi slave only ata/atapi master and ata/atapi slave compactflash only ata/atapi slave and compactflash or other removable ide master additional resources cy4615c ez-usb at2lp reference design kit usb specification version 2.0 ata specification t13/1410d revision 3b usb mass storage class bulk-only transport specification http://www.usb.org/devel- opers/devclass_docs/usbmassbulk_10.pdf usb 2.0 tranceiver cy smart usb fs/hs engine 4 kbyte fifo pll i 2 c bus master ata interface logic data control 24 mhz xtal 16 bit ata data usb d+ d- internal control logic vbus ata interface control signals misc control signals and gpio sda scl ata 3-state control reset logic block diagram [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 3 of 44 contents introduction ....................................................................... 4 cy7c68300a compatibility .............................................. 4 pin diagrams ..................................................................... 5 pin descriptions ............................................................... 9 additional pin descriptions .. ...................................... 13 hid functions for button controls ............................... 15 functional overview ...................................................... 16 usb signaling speed ............. .............. .............. ....... 16 ata interface ............................................................ 16 operating modes ............................................................ 19 operational mode selection fl ow ............................. 19 fused memory data .................................................. 20 normal mass storage mode ...................................... 20 board manufacturing test mode ............................... 20 eeprom organization .. .............. ........... ........... ....... 22 programming the eeprom ...................................... 35 absolute maximum ratings .......................................... 36 operating conditions ..................................................... 36 dc characteristics ......................................................... 36 ac electrical characteristics ........................................ 37 ata timing characteristics ....................................... 37 usb transceiver characterist ics .............................. 37 ordering information ...................................................... 37 ordering code definitions ..... .................................... 37 package diagrams .......................................................... 38 general pcb layout recommendations for usb mass storage designs ..................................... 40 quad flat package no leads (qfn) package design notes ................................................... 40 other design considerations ........................................ 41 proper power up sequence ...................................... 41 ide removable media devices ................................. 41 devices with small buffers ....................................... 41 acronyms ........................................................................ 42 document conventions ................................................. 42 units of measure ....................................................... 42 document history page ................................................. 43 sales, solutions, and legal information ...................... 44 worldwide sales and design s upport ......... .............. 44 products .................................................................... 44 psoc solutions ......................................................... 44 [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 4 of 44 introduction the ez-usb at2lp ? (cy7c68300c/cy7c68301c and cy7c68320c/cy7c68321c) implements a fixed-function bridge between one usb port and one or two ata- or atapi-based mass storage device ports. this bridge adheres to the mass storage class bulk-only transport specification (bot) and is intended for bus and self powered devices. the at2lp is the latest addition to the cypress usb mass storage portfolio, and is an ideal cost- and power-reduction path for designs that previously used cypress?s isd-300a1, isd-300lp, or ez-usb at2. specifically, the cy7c68300c/cy7c68301c includes a mode that makes it pin-for-pin co mpatible with the ez-usb at2 (cy7c68300a). the usb port of cy7c68300c/301c and cy7c68320c/321a (at2lp) is connected to a host computer directly or with the downstream port of a usb hub. software on the usb host system issues commands and sends data to the at2lp and receives status and data from the at2lp using standard usb protocol. the ata/atapi port of the at2lp is connected to one or two mass storage devices. a 4 kbyte buffer maximizes ata/atapi data transfer rates by minimi zing losses due to device seek times. the ata interface supports ata pio modes 0, 3, and 4, multiword dma mode 2, and ultra dma modes 2, 3, and 4. the device initialization process is configurable, enabling the at2lp to initialize ata/atapi devices without software intervention. cy7c68300a compatibility as mentioned in the previous section, the cy7c68300c/301c contains a backward compatibility mode that enables it to be used in existing ez-usb at2 (cy7c68300a) designs. the backward compatibility mode is enabled by programming the eeprom with the cy7c68300a signature. during startup, the at2lp checks the i 2 c bus for an eeprom with a valid signature in the firs t two bytes. if the signature is 0x4d4d, the at2lp configures itse lf for pin-to-pin compatibility with the at2 and begins normal mass storage operation. if the signature is 0x534b, the at2lp co nfigures itself with the at2lp pinout and begins normal mass storage operation. refer to the logic flow in figure 1 for more information on the pinout selection process. most designs that us e the at2 can migrate to the at2lp with no changes to either the board la yout or eeprom data. cypress has published an application note focused on migrating from the at2 to the at2lp to help expedite the process. it can be downloaded from the cypress website ( http://www.cypress.com ) or obtained through a cypress representative. figure 1. simplified pinout selection flowchart read eeprom eeprom signature 0x4d4d? yes set ez-usb at2 (cy7c68300a) pinout set ez-usb at2lp (cy7c68300b) pinout no normal operation [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 5 of 44 pin diagrams the at2lp is available in different package types to meet a va riety of design needs. the cy7c68320c/321c is available in 56-pin qfn and 100-pin tqfp packages to provide the greatest flexibility fo r new designs. the cy7c68300c is available in 56-pin ssop and qfn package types and cy7c68301c is available in qfn pa ckage to ensure backward compatibility with cy7c68300a designs. figure 2. 56-pin ssop pinout (cy7c68300c only) note labels in italics denote pin functional ity during cy7c68300a compatibility mode. 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1 2 3 4 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 56 55 54 53 atapuen ( gnd ) vcc gnd iordy dmarq avcc xtalout xtalin agnd vcc dplus dminus gnd vcc gnd pwr500 # ( pu 10k ) gnd ( reserved ) scl sda vcc dd0 dd1 dd2 dd3 dd13 dd14 dd15 gnd dd8 ( ata_en ) vbus_ ata_enable vcc reset# gnd areset # ( vbus_ pwr_ valid ) da2 cs1# cs0# ( da2 ) drvpwrvld da1 da0 intrq vcc dmack # dior # diow # gnd vcc gnd dd7 dd6 dd5 dd4 dd12 dd11 dd10 dd9 [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 6 of 44 figure 3. 56-pin qfn pinout (cy7c68300c/cy7c68301c) note italic labels denote pin functionalit y during cy7c68300a compatibility mode. reset# gnd areset# da2 ( vbus_pwr_valid ) cs1# cs0# drvpwrvld ( da2 ) da1 da0 intrq vcc dmack# dior# diow# iordy dmarq avcc xtalout xtalin agnd vcc dplus dminus gnd vcc gnd (pu10k) pwr500# gnd 15 16 17 18 19 20 21 22 23 24 25 26 27 28 scl sda vcc dd0 dd1 dd2 dd3 dd4 dd5 dd6 dd7 gnd vcc gnd 42 41 40 39 38 37 36 35 34 33 32 31 30 29 56 55 54 53 52 51 50 49 48 47 46 45 44 43 1 2 3 4 5 6 7 8 9 10 11 12 13 14 gnd vcc atapuen ( nc ) gnd dd15 dd14 dd13 dd12 dd11 dd10 dd9 dd8 vbus_ata_enable ( ata_en ) vcc [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 7 of 44 figure 4. 56-pin qfn pinout (cy7c68320c/cy7c68321c) gnd vcc gpio2 gnd dd15 dd14 dd13 dd12 dd11 dd10 dd9 dd8 vbus_ata_enable vcc reset# gnd areset# da2 cs1# cs0# gpio0 da1 da0 intrq vcc dmack# dior# diow# iordy dmarq avcc xtalout xtalin agnd vcc dplus dminus gnd vcc gnd gpio1 gnd scl sda vcc dd0 dd1 dd2 dd3 dd4 dd5 dd6 dd7 gnd vcc gnd 15 16 17 18 19 20 21 22 23 24 25 26 27 28 42 41 40 39 38 37 36 35 34 33 32 31 30 29 56 55 54 53 52 51 50 49 48 47 46 45 44 43 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 8 of 44 figure 5. 100-pin tqfp pinout (cy7c68320c/cy7c68321c only) 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 dd8 vbus_ata_enable vcc reset# nc gnd areset# da2 cs1# cs0# drvpwrvld da1 da0 intrq vcc gnd nc nc vbuspwrd nc nc nc lowpwr# nc dmack# dior# diow# vcc nc nc vcc gnd iordy dmarq gnd gnd gnd gnd avcc xtalout xtalin agnd nc nc nc vcc dplus dminus gnd vcc gnd sysirq gnd gnd gnd pwr500# gnd nc scl sda 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 nc nc vcc dd0 dd1 dd2 dd3 vcc gnd nc gnd nc gnd dd4 dd5 dd6 dd7 gnd vcc gnd atapuen gnd dd15 dd14 dd13 dd12 gnd gpio5 gpio4 gpio3 gpio2 gpio1 gpio0 nc nc vcc gnd dd11 dd10 dd9 [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 9 of 44 pin descriptions the following table lists the pinouts for the 56-pin ssop, 56-pin qfn, and 100-pin tqfp package options for the at2lp. refer to the pin diagrams on page 5 for differences between the 68300c/01c and 68320c/321c pinouts for the 56-pin packages. for information on the cy7c68300a pinout, refer to the cy7c68300a data sheet that is found in the ?ez-usb at2? folder of the cy4615c reference design kit cd . table 1. at2lp pin descriptions note italic pin names denote pin functional ity during cy7c68300a compatibility mode 100 tqfp 56 qfn 56 ssop pin name pin type default state at startup pin description 1 55 6 v cc pwr v cc . connect to 3.3 v power source. 2 56 7 gnd gnd ground . 3 1 8 iordy i [1] input ata control . apply a 1k pull up to 3.3 v. 4 2 9 dmarq i [1] input ata control . 5 6 7 8 n/a n/a gnd ground . 9 3 10 av cc pwr analog v cc . connect to v cc through the shortest path possible. 10 4 11 xtalout xtal xtal 24 mhz crystal output . (see xtalin, xtalout on page 13 ). 11 5 12 xtalin xtal xtal 24 mhz crystal input . (see xtalin, xtalout on page 13 ). 12 6 13 agnd gnd analog ground . connect to ground with as short a path as possible. 13 14 15 n/a n/a nc no connect . 16 7 14 v cc pwr v cc . connect to 3.3 v power source. 17 8 15 dplus i/o high z usb d+ signal (see dplus, dminus on page 13 ). 18 9 16 dminus i/o high z usb d?signal (see dplus, dminus on page 13 ). 19 10 17 gnd gnd ground . 20 11 18 v cc pwr v cc . connect to 3.3 v power source. 21 12 19 gnd gnd ground . 22 n/a n/a sysirq i input usb interrupt request . (see sysirq on page 13 ). active high. connect to gnd if functionality is not used. 23 24 25 n/a n/a gnd gnd ground . 26 [2] 13 [2] 20 pwr500# [3] ( pu 10k ) o bmaxpower request granted indicator . (see pwr500# on page 15 ). active low. n/a for cy7c68320c/cy7c68321c 56-pin packages. 27 14 21 gnd ( reserved ) reserved . tie to gnd. 28 n/a n/a nc no connect . 29 15 22 scl o active for several ms at startup. clock signal for i 2 c interface . (see scl, sda on page 13 ). apply a 2.2k pull up resistor. notes 1. if byte 8, bit 4 of the eeprom is set to ?0?, the ata in terface pins are only active when vbus_ata_en is asserted. see vbus_ata_enable on page 15 . 2. the general purpose inputs can be enabled on atapuen, pwr500#, and drvpwrvld via eeprom byte 8, bit 7 on cy7c68320c/cy7c68321 c. 3. a ?#? sign after the pin name indicates that it is active low. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 10 of 44 30 16 23 sda i/o data signal for i 2 c interface . (see scl, sda on page 13 ). apply a 2.2k pull up resistor. 31 32 n/a n/a nc no connect . 33 17 24 v cc pwr v cc . connect to 3.3 v power source. 34 18 25 dd0 i/o [4] high z ata data bit 0 . 35 19 26 dd1 i/o [4] high z ata data bit 1 . 36 20 27 dd2 i/o [4] high z ata data bit 2 . 37 21 28 dd3 i/o [4] high z ata data bit 3 . 38 n/a n/a v cc pwr v cc . connect to 3.3 v power source. 39 n/a n/a gnd gnd ground . 40 n/a n/a nc nc no connect . 41 n/a n/a gnd ground . 42 n/a n/a nc nc no connect . 43 n/a n/a gnd ground . 44 22 29 dd4 i/o [4] high z ata data bit 4 . 45 23 30 dd5 i/o [4] high z ata data bit 5 . 46 24 31 dd6 i/o [4] high z ata data bit 6 . 47 25 32 dd7 i/o [4] high z ata data bit 7 . apply a 1k pull down to gnd. 48 26 33 gnd gnd ground . 49 27 34 v cc pwr v cc . connect to 3.3 v power source. 50 28 35 gnd gnd ground . 51 52 n/a n/a nc nc no connect . 53 n/a n/a v cc pwr v cc . connect to 3.3 v power source. 54 29 36 diow# [5] o/z [4] driven high (cmos) ata control . 55 30 37 dior# o/z [4] driven high (cmos) ata control . 56 31 38 dmack# o/z [4] driven high (cmos) ata control . 57 n/a n/a nc nc no connect . 58 n/a n/a lowpwr# o usb suspend indicator . (see lowpwr# on page 14 ). 59 60 61 n/a n/a nc nc no connect . 62 n/a n/a vbuspwrd i input bus powered mode selector . (see vbuspwrd on page 15 ). 63 64 n/a n/a nc nc no connect . 65 n/a n/a gnd gnd ground . 66 32 39 v cc pwr v cc . connect to 3.3 v power source. table 1. at2lp pin descriptions (continued) note italic pin names denote pin functional ity during cy7c68300a compatibility mode 100 tqfp 56 qfn 56 ssop pin name pin type default state at startup pin description notes 4. if byte 8, bit 4 of the eeprom is set to ?0?, the ata in terface pins are only active when vbus_ata_en is asserted. see vbus_ata_enable on page 15 . 5. a ?#? sign after the pin name indicates that it is active low. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 11 of 44 67 33 40 intrq i [6] input ata interrupt request . 68 34 41 da0 o/z [6] driven high after 2 ms delay ata address . 69 35 42 da1 o/z [6] driven high after 2 ms delay ata address . 70 [7] 36 [7] 43 drvpwrvld ( da2 ) i input device presence detect. (see drvpwrvld on page 14 ). configurable l ogical polarity is cont rolled by eeprom address 0x08. this pin must be pulled high if functionality is not used. alternate function. input when the eepr om configuration byte 8 has bit 7 set to ?1?. the input value is reported through ep1in (byte 0, bit 0). 71 37 44 cs0# o/z [6] driven high after 2 ms delay ata chip select . 72 38 45 cs1# o/z [6] driven high after 2 ms delay ata chip select . 73 39 46 da2 ( vbus_pwr_valid ) o/z [6] driven high after 2 ms delay ata address . 74 40 47 areset# o/z [6] ata reset . 75 41 48 gnd gnd ground . 76 n/a n/a nc nc no connect . 77 42 49 reset# i input chip reset (see reset# on page 15 ). 78 43 50 v cc pwr v cc . connect to 3.3 v power source. 79 44 51 vbus_ata_enable ( ata_en ) i input vbus detection (see vbus_ata_enable on page 15 ). 80 45 52 dd8 i/o [6] high z ata data bit 8 . 81 46 53 dd9 i/o [6] high z ata data bit 9 . 82 47 54 dd10 i/o [6] high z ata data bit 10 . 83 48 55 dd11 i/o [6] high z ata data bit 11 . 84 n/a n/a gnd ground . 85 n/a n/a v cc pwr v cc . connect to 3.3 v power source. 86 87 n/a n/a nc nc no connect . 88 89 90 91 92 93 36 [7] 13 [7] 54 [7] n/a gpio0 gpio1 gpio2 gpio3 gpio4 gpio5 i/o [7] general purpose i/o pins (see gpio pins on page 14 ). the gpio pins must be tied to gn d if functionality is not used. 94 n/a n/a gnd gnd ground . table 1. at2lp pin descriptions (continued) note italic pin names denote pin functional ity during cy7c68300a compatibility mode 100 tqfp 56 qfn 56 ssop pin name pin type default state at startup pin description notes 6. if byte 8, bit 4 of the eeprom is set to ?0?, the ata in terface pins are only active when vbus_ata_en is asserted. see vbus_ata_enable on page 15 . 7. the general purpose inputs can be enabled on atapuen, pwr500#, and drvpwrvld via eeprom byte 8, bit 7 on cy7c68320c/cy7c68321 c. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 12 of 44 95 49 56 dd12 i/o [8] high z ata data bit 12 . 96 50 1 dd13 i/o [8] high z ata data bit 13 . 97 51 2 dd14 i/o [8] high z ata data bit 14 . 98 52 3 dd15 i/o [8] high z ata data bit 15 . 99 53 4 gnd gnd ground . 100 [9] 54 [9] 5 atapuen ( nc ) i/o bus powered ata pull up voltage source (see atapuen on page 15 ). alternate function : general purpose input when the eeprom configuration byte 8 has bit 7 set to ?1?. the input value is reported through ep1in (byte 0, bit 2). table 1. at2lp pin descriptions (continued) note italic pin names denote pin functional ity during cy7c68300a compatibility mode 100 tqfp 56 qfn 56 ssop pin name pin type default state at startup pin description notes 8. if byte 8, bit 4 of the eeprom is set to ?0?, the ata in terface pins are only active when vbus_ata_en is asserted. see vbus_ata_enable on page 15 . 9. the general purpose inputs can be enabled on atapuen, pwr500#, and drvpwrvld via eeprom byte 8, bit 7 on cy7c68320c/cy7c68321 c. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 13 of 44 additional pin descriptions the following sections provide additional pin information. dplus, dminus dplus and dminus are the usb signaling pins; they must be tied to the d+ and d? pins of the usb connector. because they operate at high frequencies, the usb signals require special consideration when designing the layout of the pcb. see general pcb layout recommendations for usb mass storage designs on page 40 for pcb layout recommendations. when reset# is released, the a ssertion of the internal pull up on d+ is gated by a combi nation of the state of the vbus_ata_enable pin, the value of configuration address 0x08 bit 0 (drvpwrvld enable), and the detection of a non-removable ata/atapi drive on the ide bus. see table 2 for a description of this relationship. scl, sda the clock and data pins for the i 2 c port must be connected to the configuration eeprom and to 2.2k pull up resistors tied to v cc . if no eeprom is used in t he design, the scl and sda pins must still be connected to pu ll up resistors. the scl and sda pins are active for several milliseconds at startup. xtalin, xtalout the at2lp requires a 24 mhz ( ? 100 ppm) signal to derive internal timing. typically, a 24 mhz (12 pf, 500 ? w, parallel-resonant, fundamental mode) crystal is used, but a 24 mhz square wave (3.3 v, 50/50 duty cycle) from another source can also be used. if a crystal is used, connect its pins to xtalin and xtalout, and also through 12 pf capacitors to gnd as shown in figure 6 . if an alternate clock source is used, apply it to xtalin and leave xtalout unconnected. figure 6. xtalin/xtalout diagram sysirq the sysirq pin provides a way for systems to request service from host software by using the usb interrupt pipe on endpoint 1 (ep1). if the at2lp has no pendi ng interrupt da ta to return, usb interrupt pipe data requests are nak?ed. if pending data is available, the at2lp returns 16 bits of data. this data indicates whether at2lp is operating in high speed or full speed, whether the at2lp is reporting self powered or bus powered operation, and the states of any gpio pins that are configured as inputs. gpio pins can be individually set as inputs or outputs, with byte 0x09 of the configuration data. th e state of any gpio pin that is not set as an input is reported as ?0? in the ep1 data. ta b l e 3 gives the bitmap for the data returned on the interrupt pipe and figure 7 on page 14 depicts the latching algorithm incorporated by the at2lp. the sysirq pin must be pulled low if hid functionality is used. refer to hid functions for button controls on page 15 for more details on hid functionality. table 2. d+ pull up assertion dependencies vbus_ata_en111100 drvpwrvld enable bit110011 ata/atapi drive detected yesnoyesnoyesno state of d+ pull up111000 24mhz xtal 12pf xtalin xtalout 12pf table 3. interrupt data bitmap ep1 data byte 1 ep1 data byte 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 reserved reserved reserved reserved reserved reserved usb high speed vbus powered reserved reserved gpio[5] gpio[4] gpio[3] gpio[2] gpio[1] gpio[0] [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 14 of 44 figure 7. sysirq latching algorithm drvpwrvld when this pin is enabled with bi t 0 of configuration address 0x08 (drvpwrvld enable), the at2lp informs the host that a removable device, such as a cf card, is present. the at2lp uses drvpwrvld to detect that the removable device is present. pin polarity is contro lled by bit 1 of configuration address 0x08. when drvpwrvld is deasserted, the at2lp reports a ?no media present? status (asc = 0x3a, asq = 0x00) when queried by the host. when th e media is detected again, the at2lp reports a ?media changed? status to the host (asc = 0x28, asq = 0x00) when queried. when a removable device is used, it is always considered by the at2lp to be the ide master device. only one removable device may be attached to the at2lp. if the system only contains a removable device, bit 6 of configuration address 0x08 (search ata bus) must be set to ?0? to disable ata device detection at startup. if a non-removable device is connected in addition to a removable media device, the non removable device must be configured as ide slave (device address 1). gpio pins the gpio pins enable a general purpose input and output interface. there are several differ ent interfaces to the gpio pins: configuration bytes 0x09 and 0x0a contain the default settings for the gpio pins upon init ial at2lp configuration. the host can modify the settings of the gpio pins during operation. this is done with vendor-specific commands described in programming the eeprom on page 35 . the status of the gpio pins is returned on the interrupt endpoint (ep1) in response to a sysirq. see sysirq on page 13 for sysirq details. lowpwr# lowpwr# is an output pin that is driven to ?0? when the at2lp is not in suspend. lowpwr# is placed in high z when the at2lp is in a suspend state. this pin only indicates the state of the at2lp and must not be used to determine the status of the usb host because of variations in the behavior of different hosts. usb interrupt pipe polled? yes no nak request sysirq=1? latch state of io pins set int_data = 1 int_data = 1? no return interrupt data set int_data = 0 yes yes no yes int_data = 0 and sysirq=0? no [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 15 of 44 ata interface pins the ata interface pins must be connected to the corresponding pins on an ide connector or mass storage device. to enable sharing of the ide bus with other master devices, the at2lp can place all ata interface pins in a high z state whenever vbus_ata_enable is not asserted. enabling this feature is done by setting bit 4 of configuration address 0x08 to ?1?. otherwise, the ata bus is driven by the at2lp to a default inactive state whenever vbus_ata_enable is not asserted. design practices for signal integrity as outlined in the ata/atapi-6 specification must be followed wi th systems that use a ribbon cable interconnect between the at2lp?s ata interface and the attached ma ss storage device, especially if ultra dma mode is used. vbus_ata_enable vbus_ata_enable is typically used to indicate to the at2lp that power is present on vbus. this pin is polled by the at2lp at startup and then every 20 ms thereafter. if this pin is ?0?, the at2lp releases the pull up on d+ as required by the usb specification. also, if bit 4 of configuration add ress 0x08 is ?1?, the ata interface pins are placed in a high z state when vbus_ata_enable is ?0?. if bit 4 of configuration addr ess 0x08 is ?0?, the ata interface pins are still driven when vbus_ata_enable is ?0?. atapuen this output can be used to co ntrol the required host pull up resistors on the ata interface in a bus powered design to minimize unnecessary power consumption when the at2lp is in suspend. atapuen is driven to ?0? when the ata bus is inactive. atapuen is driven to ?1? when the ata bus is active. atapuen is set to a high z state along with all other ata interface pins if vbus_ata_enable is deasserted and the ata_en functionality (bit 4 of configurat ion address 0x08) is enabled (0). atapuen can also be configured as a gpio input. see hid functions for button controls on page 15 for more information on hid functionality. pwr500# the at2lp asserts pwr500# to indicate that vbus current may be drawn up to the limit specified by the bmaxpower field of the usb configuration descriptors. if the at2lp enters a low-power state, pwr500# is deasserted. when normal operation is resumed, pwr500# is restored. the pwr500# pin must never be used to control power sources for the at2lp. in the 56-pin package, pwr500# only functions during bus powered operation. pwr500# can also be configured as a gpio input. see hid functions for button controls on page 15 for more information on hid functionality. vbuspwrd vbuspwrd is used to indicate self or bus powered operation. some designs require the ability to operate in either self- or bus powered modes. the vbuspwrd input pin enables these devices to switch between self powered and bus powered modes by changing the contents of the bmaxpower field and the self powered bit in the reported c onfiguration descriptors (see ta b l e 4 ). note that current usb host drivers do not poll the device for this information, so the effect of this pin is only seen on a usb or power on reset. reset# asserting reset# for 10 ms resets the entire at2lp. in self powered designs, this pin is normally tied to v cc through a 100k resistor, and to gnd through a 0.1 ? f capacitor, as shown in figure 8 . cypress does not recommend an rc reset circuit for bus powered devices because of the potential for vbus voltage drop, which may result in a star tup time that exceeds the usb limit. refer to the application note titled ez-usb fx2 ? /at2 ? /sx2 ? reset and power considerations, at www.cypress.com , for more information. while the at2lp is in reset, all pins are held at their default startup state. hid functions for button controls cypress?s cy7c68320c/cy7c68321c has the capability of supporting human interface device (hid) signaling to the host. if there is an hid descriptor in the configuration data, the gpio pins that are set as inputs are polled by the at2lp logic approximately every 17 ms (depending on other internal interrupt routines). if a change is detected in the state of any hid-enabled gpio, an hid report is sent through ep1 to the host. the report format for byte 0 and byte 1 is shown in ta b l e 5 . the ability to add buttons to a mass storage solution opens new applications for data backup and other device-side notification to the host. the at2lp blaster software, found in the cy4615c table 4. behavior of descriptor data that is dependent upon vbuspwrd state pin vbuspwrd = ?1? vbuspwrd = ?0? vbuspwrd n/a (56-pin) bmaxpower reported value 0xfa (500 ma) 0x01 (2 ma) the value from configuration address 0x34 is used. bmattributes bit 6 reported value ?0? (bus powered) ?1? (self powered) ?0? if bmaxpower ? 0x01 ?1? if bmaxpower ? 0x01 figure 8. r/c reset circuit for self powered designs 100k ? 0.1 ? f reset# [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 16 of 44 files, provides an easy way to enable and modify the hid features of the at2lp. gpio pins can be individually set as inputs or outputs, with byte 0x09 of the configuration data, enabling a mix of hid and general purpose outputs. gpios that are not configured as inputs are reported with a value of ?0? in the hid data. the reserved bits? values must be ignored, and cypress recommends using a bitmask in software to filter out unused hid data. note that if using the 56-pin package, the reported gpio[5:3] values must be ignored becaus e the pins are not actually present. functional overview chip functionally is described in the subsequent sections. usb signaling speed at2lp operates at the followi ng two rates defined in the usb 2.0 specification dated april 27, 2000: full-speed, with a signaling bit rate of 12 mbits/sec. high-speed, with a signaling bit rate of 480 mbits/sec. at2lp does not operate at the low-speed signaling rate of 1.5 mbits/sec. ata interface the ata/atapi port on the at2lp is compatible with the information technology?at atta chment with packet interface?6 (ata/atapi-6) specification, t13/1410d revision 2a . the at2lp supports both atapi packet commands and ata commands (by use of ata command blocks), as outlined in ata command block (atacb) on page 16 . refer to the usb mass storage class (msc) bulk-only transport (bot) specification for information on command block formatting. additionally, the at2lp translates atapi sff-8070i commands to ata commands for seamless integration of ata devices with generic mass storage class bot drivers. ata command block (atacb) the ata command block (atacb) functionality provides a means of passing ata commands and ata register accesses to the attached device for execution. atacb commands are transferred in the command block wrapper command block (cbwcb) portion of the command block wrapper (cbw). the atacb is distinguished from other command blocks by having the first two bytes of th e command block match the bvscbsignature and bvscbsubcommand values that are defined in ta b l e 6 . only command blocks that have a valid bvscbsignature and bvscbsubcommand are interpreted as ata command blocks. all ot her fields of the cbw and restrictions on the cbwcb rema in as defined in the usb mass storage class bulk-only transpo rt specification. the atacb must be 16 bytes in length. the following table and text defines the fields of the atacb. table 5. hid data bitmap usb interrupt data byte 1 usb interrupt data byte 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 reserved reserved reserved reserved reserved reserved usb high speed vbus powered reserved reserved gpio[5] gpio[4] gpio[3] gpio[2] gpio[1] gpio[0] table 6. atacb field descriptions byte field name field description 0 bvscbsignature this field indicates to the cy7c68300c/cy7c68301c that the atacb contains a vendor-specific command block. the value of this field must match the value in eeprom address 0x04 for the command to be recognized as a vendor-specific atacb command. 1 bvscbsubcommand this field must be set to 0x24 for atacb commands. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 17 of 44 2 bmatacbactionselect this field controls the execution of the atacb according to the bitfield values: bit 7 identifypacketdevice ? this bit indicates that the data phase of the command contains atapi (0xa1) or ata (0xec) identify device data. setting identifypacketdevice when the data phase does not contain identify device data results in unspecified device behavior. 0 = data phase does not contain identify device data 1 = data phase contains atapi or ata identify device data bit 6 udmacommand ? this bit enables supported udma device transfers. setting this bit when a non-udma capable device is attached results in undetermined behavior. 0 = do not use udma device transfers (only use pio mode) 1 = use udma device transfers bit 5 devoverride ? this bit determines whether the dev bit value is taken from the value assigned to the lun during startup or from the atacb. 0 = the dev bit is taken from the value assigned to the lun during startup 1 = the dev bit is taken from the atacb field 0x0b, bit 4 bit 4 derroroverride ? this bit controls the device error override feature. this bit must not be set during a bmatacbactionselect taskfileread. 0 = data accesses are halted if a device error is detected 1 = data accesses are not halted if a device error is detected bit 3 perroroverride ? this bit controls the phase error override feature. this bit must not be set during a bmatacbactionselect taskfileread. 0 = data accesses are halted if a phase error is detected 1 = data accesses are not halted if a phase error is detected bit 2 pollaltstatoverride ? this bit determines whether or not the alternate status register is polled and the bsy bit is used to qualify the atacb operation. 0 = the altstat register is polled until bsy=0 before proceedi ng with the atacb operation 1 = the atacb operation is executed wi thout polling the altstat register. bit 1 deviceselectionoverride ? this bit determines when the device selection is performed in relation to the command register write accesses. 0 = device selection is performed be fore command register write accesses 1 = device selection is performed foll owing command register write accesses bit 0 taskfileread ? this bit determines whether or not the taskfile register data selected in bmatacbregisterselect is returned. if this bit is set, the dcbwdatatransferlength field must be set to 8. 0 = execute atacb command and data transfer (if any) 1 = only read taskfile registers selected in bmatacbregisterselect and return 0x00h for all others. the format of the 8 bytes of returned data is as follows: ? address offset 0x00 (0x3f6) ? alternate status ? address offset 0x01 (0x1f1) ? features/error ? address offset 0x02 (0x1f2) ? sector count ? address offset 0x03 (0x1f3) ? sector number ? address offset 0x04 (0x1f4) ? cylinder low ? address offset 0x05 (0x1f5) ? cylinder high ? address offset 0x06 (0x1f6) ? device/head ? address offset 0x07 (0x1f7) ? command/status table 6. atacb field descriptions (continued) byte field name field description [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 18 of 44 3 bmatacbregisterselect this field controls which of the taskfile register read or write accesses occur. taskfile read data is always 8 bytes in length, and unselected register data are returned as 0x00. register accesses occur in sequential order as outlined here (0 to 7): bit 0 (0x3f6) device control/alternate status bit 1 (0x1f1) features/error bit 2 (0x1f2) sector count bit 3 (0x1f3) sector number bit 4 (0x1f4) cylinder low bit 5 (0x1f5) cylinder high bit 6 (0x1f6) device/head bit 7 (0x1f7) command/status 4 batacbtransferblockcount this value indicates the maximum requested block size be in 512-byte increments. this value must be set to the last value used for the ?sectors per block? in the set_multiple_mode command. legal values are 0, 1, 2, 4, 8, 16, 32, 64, and 128 where ?0? indicates 256 sectors per block. a command failed status is returned if an illegal value is used in the atacb. 5?12 batacbtaskfilewritedata these bytes contain ata r egister data used with ata command or pio write operations. only registers selected in bmatacbregisterselect are required to hold valid data when accessed. the registers are as follows. atacb address offset 0x05 (0x3f6) ? device control atacb address offset 0x06 (0x1f1) ? features atacb address offset 0x07 (0x1f2) ? sector count atacb address offset 0x08 (0x1f3) ? sector number atacb address offset 0x09 (0x1f4) ? cylinder low atacb address offset 0x0a (0x1f5) ? cylinder high atacb address offset 0x0b (0x1f6) ? device atacb address offset 0x0c (0x1f7) ? command 13?15 reserved these bytes must be set to 0x00 for atacb commands. table 6. atacb field descriptions (continued) byte field name field description [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 19 of 44 operating modes the different modes of operation and eeprom in formation are presented in the following sections. operational mode selection flow during the power up sequence, the at2lp queries the i 2 c bus for an eeprom. the at2lp then selects a pinout configuration as shown here, and checks to see if areset# is co nfigured for board manu facturing test mode. if no eeprom is detected, the at2lp uses the values in the factory-programmable (f used) memory space. see fused memory data on page 20 for more information. this is not a valid mode of operation if no factory programming has been done. if an eeprom signature of 0x4d4d is f ound, the cy7c68300c/cy7c68301c uses the same pinout and eeprom format as the cy7c68300a (ez-usb at2+). if an eeprom signature of 0x534b is found, t he at2lp uses the values stored in the eeprom to configure the usb descriptors for normal operation. if an eeprom is detected, but an invali d signature is read, the at2lp defaults into board manufact uring test mode. figure 9. operational mode selection flow no dd7 pin set high board manufacturing test mode normal mass storage mode check i 2 c bus load fused memory data (at2lp pinout) set ez-usb at2+ (cy7c68300a) pinout set ez-usb at2lp pinout areset# pin low? no yes no no yes yes signature 0x534b? eeprom found? yes signature 0x4d4d? vbus_ata_enable pin high? yes yes no areset# pin high? [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 20 of 44 fused memory data when no eeprom is detected at startup, the at2lp enumerates with the vi d/pid/did values that are stored in the fused memory space. these values can be programmed into the at2lp during chip manufacturing for high volume applications to avoid the need for an external eeprom in some designs. contact your local cypress semiconductor sales office for more information on this feature. if no factory programming has been done, the values returned from the fused memory space wo uld all be 0x00, which is not a valid mode of operation. in this case the chip uses the manufacturing mode and return the default descriptors (vid/pid of 0x4b4/0x6830). an eeprom must be used with designs that do not use factory-programmed chips to identify the device as your company?s product. normal mass storage mode in normal mass storage mode, the chip behaves as a usb 2.0 to ata/atapi bridge. this includes all typical usb device states such as powered and configured. the usb descriptors are returned according to the values stored in the external eeprom or fused memory space. a unique serial number is required for mass storage class bulk-only transport compliance, which is one reason why an eeprom or factory-programmed part is needed. board manufacturing test mode in board manufacturing test mode the at2lp behaves as a usb 2.0 device but the ata/atapi interface is not fully active. this mode must not be used for mass storage operation in a finished design. in this mode, the at2lp enable reading from and writing to the eeprom, and fo r board level te sting, through vendor- specific atapi commands utilizing the cbw command block as described in the usb mass storage class bulk-only transport specification . there is a vendor-specific atapi command for eeprom accesses (cfgcb) and one for board level testing (mfgcb), as described in the following sections. there is a convenient method available for starting the at2lp in board manufacturing test mode to enable reprogramming of eeproms without a mass storage device attached. if the ata reset (areset#) line is low on power up, the at2lp enters board manufacturing test mode. it is recommended that a 10k resistor be used to pull areset# to low. an easy way to pull the areset# line low is to short pins 1 and 3 on the 40-pin ata connector with a 10k resistor, that ties the areset# line to the required pull down on dd7. cfgcb the cfg_load and cfg_read v endor-specific commands are passed down through the bulk pipe in the cbwcb portion of the cbw. the format of this cfgcb is shown as follows. byte 0 is a vendor-specific command designator whose value is configurable and set in the configuration data (address 0x04). byte 1 must be set to 0x26 to identify it as a cfgcb command. byte2 is reserved and must be set to zero. byte 3 is used to determine the memory source to write/read. for the at2lp, this byte must be set to 0x02, in dicating the eeprom is present. bytes 4 and 5 are used to determine the start address, which must always be 0x0000. bytes 6 through 15 are reserved and must be set to zero. the data transferred to the eepr om must be in the format specified in table 11 on page 23 of this data sheet. maximum data transfer size is 255 bytes. the data transfer length is determined by the cbw data transfer length specified in bytes 8 through 11 (dcbwdatatransferlength) of the cbw (refer to table 7 ). the type/direction of the command is determined by the direction bit specified in byte 12, bit 7 (bmcbwflags) of the cbw (refer to ta b l e 7 ). table 7. command block wrapper bits offset 7 6 5 4 3 2 1 0 0?3 dcbwsignature 4?7 dcbwtag 8?11 (08h?0bh) dcbwdatatransferlength 12 (0ch) bwcbwflags dir obsolete reserved (0) 13 (0dh) reserved (0) bcbwlun 14 (0eh) reserved (0) bcbwcblength 15?30 (0fh1eh) cbwcb (cfgcb or mfgcb) [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 21 of 44 mfgcb the mfg_load and mfg_read vendor-specific commands are passed down through the bulk pipe in the cbwcb portion of the cbw. the format of this mfgcb is shown as follows. byte0 is a vendor-specific command designator whose value is configurable and set in the at2lp configuration data. byte 1 must be 0x27 to identify a mf gcb. bytes 2 through 15 are reserved and must be set to zero. the data transfer length is determined by the cbw data transfer length specified in bytes 8 through 11 (dcbwdatatransferlength) of the cbw. the type and direction of the command is determined by the direction bit specified in byte 12, bit 7 (bmcbwflags) of the cbw. mfg_load during a mfg_load, the at2lp enters into manufacturing test mode. manufacturing test mode is provided as a means to implement board or system level interconnect tests. during manufacturing test mode operation, all outputs not directly associated with usb operation are controllable. normal control of the output pins are disabled. control of the select at2lp i/o pins and their tri-state controls are mapped to the atapi data packet associated with this request. (see table 10 for an explanation of the required mfg_load data format.) any data length can be specified, but onl y bytes 0 through 3 are mapped to pins, so a length of 4 bytes is recommended. to exit manufacturing test mode, a ha rd reset (toggle reset#) is required. mfg_read this usb request returns a ?snapshot? of select at2lp input pins. at2lp input pins not directly associated with usb operation can be sampled at any time during manufacturing test mode operation. see table 10 for an explanation of the mfg_read data format. any data length can be specified, but only bytes 0 through 3 contain usable information, so a length of 4 bytes is recommended. table 8. example cfgcb offset cfgcb byte description bits 76543210 0 bvscbsignature (set in configuration bytes) 00100100 1 bvscbsubcommand (must be 0x26) 00100110 2 reserved (must be set to zero) 00000000 3 data source (must be set to 0x02) 00000010 4 start address (lsb) (must be set to zero) 00000000 5 start address (msb) (must be set to zero) 00000000 6?15 reserved (must be set to zero) 00000000 table 9. example mfgcb offset mfgcb byte description bits 76543210 0 0 bvscbsignature (set in configuration bytes) 00100100 1 1 bvscbsubcommand (hardcoded 0x27) 00100111 2?15 2?15 reserved (must be zero) 0 0 0 0 0 0 0 0 table 10. mfg_read and mfg_load data format byte bits read/load function 0 7 r/l areset# 6rda2 5:4 r/l cs#[1:0] 3 r/l drvpwrvld 2:1 r/l da[1:0] 0rintrq 1 7 l dd[15:0] high z status 0 = high z all dd pins 1 = drive dd pins 6rmfg_sel 0 = mass storage mode 1 = manufacturing mode 5 r vbus_ata_enable 4rdmarq 3 r iordy 2r/ldmack# 1r/ldior# 0r/ldiow# 2 7:0 r/l dd[7:0] 3 7:0 r/l dd[15:8] [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 22 of 44 eeprom organization the contents of the recommended 256-byte (2048-bit) i 2 c eeprom are arranged as follows. in ta b l e 11 , the column labeled ?required contents? contains the values that must be used for proper operation of the at2lp. the column labeled ?variable contents? contains suggested entries and values that may vary (such as string leng ths) according to the eeprom data. some values, such as the vendor id, product id and device serial number, must be customized to meet usb compliance. the ?at2lp blaster? tool in the cy4615c kit can be used to edit and program these values into an at2lp-based product (refer to figure 10 ). the ?at2lp primer? tool can be used to program at2lp-based products in a manufacturing environment and provides for serial number randomization. see board manufacturing test mode on page 20 for details on how to use vendor-specific atapi commands to read and program the eeprom. the address pins on the serial eeprom must be set such that the eeprom is at physical address 2 (a0 = 0, a1 = 1, a2 = 0) or address 4 (a0 = 0, a1 = 0, a2 = 1) for eeprom devices that are internally byte-addressed memories. it is recommended that the address pins be set this way even on eeproms that may indicate that the address pins are internal no-connects. figure 10. snapshot of ?at2lp blaster? utility [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 23 of 44 table 11. configuration data organization byte address configuration item name configuration item description required contents variable contents note devices running in backward compatibility (cy7c68300a) mode must use the cy7c68300a eeprom organization, and not the format shown in this document. refer to the cy7c68300a data sheet for the cy7c68300a eeprom format. at2lp configuration 0x00 eeprom signature byte 0 i 2 c eeprom signature byte 0. this byte must be 0x53 for proper at2lp pin configuration. 0x53 0x01 eeprom signature byte 1 i 2 c eeprom signature byte 1. this byte must be 0x4b for proper at2lp pin configuration. 0x4b 0x02 apm value ata device automatic power management value. if an attached ata device supports apm and this field contains other than 0x00, the at2lp issues a set_features command to enable apm with this value during the drive initialization process. setting apm value to 0x00 disables this functionality. this value is ignored with atapi devices. 0x00 0x03 reserved must be set to 0x00. 0x00 0x04 bvscbsignature value value in the first byte of the cbw cb field that designates that the cb is to be decoded as vendor-specific ata commands instead of the atapi command block. see functional overview on page 16 for more detail on how this byte is used. 0x24 0x05 reserved bits 7:6 0x07 enable mode page 8 bit 5 enable the write caching mode page (page 8). if this page is enabled, windows disables write caching by default, which limits write performance. 0 = disable mode page 8. 1 = enable mode page 8. disable wait for intrq bit 4 poll status register rather than waiting for intrq. setting this bit to ?1? improves usb bot test results but may introduce compatibility problems with some devices. 0 = wait for intrq. 1 = poll status register instead of using intrq. busy bit delay bit 3 enable a delay of up to 120 ms at each read of the drq bit where the device data length does not match the host data length. this enables the cy7c68300c/cy7c68301c to work with most devices that incorrectly clea r the busy bit before a valid status is present. 0 = no busy bit delay. 1 = use busy bit delay. short packet before stall bit 2 determines if a short packet is sent before the stall of an in endpoint. the usb mass storage class bulk-only specification enables a device to send a short or zero-length in packet before returning a stall handshake for certain cases. certain host controller drivers may require a short packet before stall. 0 = do not force a short packet before stall. 1 = force a short packet before stall. [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 24 of 44 srst enable bit 1 determines if the at2lp is to do an srst reset during drive initialization. at least one reset must be enabled. do not set srst to ?0? and skip pin rese t to ?1? at the same time. 0 = do not perform srst during initialization. 1 = perform srst during initialization. skip pin reset bit 0 skip areset# assertion. when this bit is set, the at2lp bypasses areset# during any in itialization other than power up. do not set srst enable to ?0? and skip pin reset to ?1? at the same time. 0 = allow areset# assertio n for all device resets. 1 = disable areset# assertion e xcept for chip reset cycles. 0x06 ata udma enable bit 7 enable ultra dma data transfer support for ata devices. if enabled, and if the ata device reports udma support for the indicated modes, the at2lp uses udma data transfers at the highest negotiated rate possible. 0 = disable ata device udma support. 1 = enable ata device udma support. 0xd4 atapi udma enable bit 6 enable ultra dma data transfer support for atapi devices. if enabled, and if the atapi device reports udma support for the indicated modes, the at2lp uses udma data transfers at the highest negotiated rate possible. 0 = disable atapi device udma support. 1 = enable atapi device udma support. udma modes bits 5:0 these bits select which udma modes are enabled. the at2lp operates in the highest enabled udma mode supported by the device. the at2lp supports udma modes 2, 3, and 4 only. bit 5 = reserved. must be set to ?0?. bit 4 = enable udma mode 4. bit 3 = enable udma mode 3. bit 2 = enable udma mode 2. bit 1 = reserved. must be set to ?0?. bit 0 = reserved. must be set to ?0?. 0x07 reserved bits 7:3 must be set to ?0?. 0x07 multiword dma mode bit 2 this bit enables multiword dma s upport. if this bit is set and the drive supports it, multiword dma is used. pio modes bits 1:0 these bits select which pio modes are enabled. setting to ?1? enables use of that mode with the attached drive, if the drive supports it. multiple bits may be set. the at2lp operates in the highest enabl ed pio mode supported by the device. the at2lp supports pio modes 0, 3, and 4 only. pio mode 0 is always enabled and has no corresponding configuration bit. bit 1 = enable pio mode 4. bit 0 = enable pio mode 3. table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 25 of 44 0x08 button_mode bit 7 button mode (100-pin package only). sets atapuen, pwr500# and drvpwrvld to become button inputs returned on bits 2, 1, and 0 of ep1in. this bit must be set to ?0? if the 56-pin packages are used. 0 = disable button mode. 1 = enable button mode. 0x78 search_ata_bus bit 6 search ata bus after reset to detect non-removable ata and atapi devices. systems with only a removable device (such as cf readers) must set this bit to ?0?. systems with at least one non-removable device must set this bit to ?1?. 0 = do not search for ata devices. 1 = search for ata devices. big_package bit 5 selects the 100- or 56-pin package pinout configuration. using the wrong pinout may result in unpredictable behavior. 0 = use 56-pin package pinout. 1 = use 100-pin package pinout. ata_en bit 4 drive ata bus when at2lp is in suspend. for designs in which the ata bus is shared between the at2lp and another ata master (such as an mp3 player), the at2lp can place the ata interface pins in a high z state when it enters suspend. for designs that do not share the ata bus, the ata signals must be driven while the at2lp is in suspend to avoid floating signals. 0 = drive ata signals when at2lp is in suspend. 1 = set ata signals to high z when at2lp is in suspend. reserved bit 3 reserved. this bit must be set to ?0?. reserved bit 2 reserved. this bit must be set to ?0? drive power valid polarity bit 1 configure the logical polarity of the drvpwrvld input pin. 0 = active low (?connector ground? indication) 1 = active high (power indication from device) drive power valid enable bit 0 enable the drvpwrvld pin. when this pin is enabled, the at2lp enumerates a removable ata device, such as compactflash or microdrive, as the ide master device. enabling this pin also affects other pins related to removable device operation. 0 = disable removable ata device support. 1 = enable removable ata device support. table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 26 of 44 0x09 reserved general purpose i/o pin output enable bits 7:6 reserved. must be set to zero. bits 5:0 gpio[5:0] input and output control. gpios can be individually set as inputs or outputs using these bits. 0 = high z (pin is an input). the state of the signal connected to gpio input pins is report ed in the sysirq or hid data. 1 = output enabled (pin is an output). the state of gpio output pins is controlled by the value in address 0x0a. 0x00 0x0a reserved gpio output pin state bits 7:6 reserved. must be set to zero. bits 5:0 these bits select the value driv en on the gpio pins that are configured as outputs in configuration address 0x09. 0 = drive the gpio pin low 1 = drive the gpio pin high 0x00 0x0b lun0 identify string this byte is a pointer to the start of a 24 byte ascii (non-unicode) string in the eeprom that is used as the lun0 device identifier. this string is used by many operating systems as the user-visible name fo r the drive. if this byte is 0x00, the identify device data from the drive is used instead. 0x00 0x0c lun1 identify string this byte is a pointer to the start of a 24 byte ascii (non-unicode) string in the eeprom that is used as the lun1 device identifier. this string is used by many operating systems as the user-visible name fo r the drive. if this byte is 0x00, the identify device data from the drive is used instead. 0x00 0x0d delay after reset number of 20 ms ticks to wait between at2lp startup or reset, and the first attemp t to access any drives. 0x00 0x0e reserved bits 7:5 must be set to zero. 0x00 bus powered flag bit 4 enable bus powered hdd support. this bit enables the use of drvpwrvld features withou t reporting the lun0 device as removable media. 0 = lun0 is removable media or drvpwrvld is disabled 1 = lun0 device is bus powered and non-removable enable cf udma bit 3 enable udma transfers for re movable devices. some cf devices interfere with udma transfers when more than one drive is connected to the ata bus. 0 = do not use udma transfers with removable devices (udma signals are not connected to the cf pins). 1 = allow udma transfers to be used with removable devices (udma signals are connected to the cf pins). fixed number of logical bits 2:1 assume the presence of devices and do not perform a search of the ata bus to discover the number of luns. 00 = search ata bus and determine number of luns 01 = assume only lun0 present; no ata bus search 10 = assume lun0 and lun1 present; no ata bus search 11 = assume lun0 and lun1 present; no ata bus search table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 27 of 44 search ata on vbus bit 0 search for ata devices when vbus returns. if this bit is set, the ata bus is searched for ata devices every time vbus_ata_enable is asserted. this feature enables the at2lp to be used in designs where the drive may be physically removed (such as docking stations or port replicators). 0 = search ata bus on vbus_ata_enable assertion 1 = no ata bus search on vbus_ata_enable assertion 0x0f reserved must be set to 0x00 0x00 device descriptor 0x10 blength length of device descriptor in bytes 0x12 0x11 bdescriptor type descriptor type. 0x01 0x12 bcdusb (lsb) usb specification release number in bcd 0x00 0x13 bcdusb (msb) 0x02 0x14 bdeviceclass device class 0x00 0x15 bdevicesubclass device subclass 0x00 0x16 bdeviceprotocol device protocol 0x00 0x17 bmaxpacketsize0 usb packet size supported for default pipe 0x40 0x18 idvendor (lsb) vendor id. cypress? vendor id may only be used for evaluation purposes, and not in released products. your vendor id 0x19 idvendor (msb) 0x1a idproduct (lsb) product id your product id 0x1b idproduct (msb) 0x1c bcddevice (lsb) device release number in bcd lsb (product release number) your release number 0x1d bcddevice (msb) device release nu mber in bcd msb (silicon release number) 0x1e imanufacturer index to manufacturer st ring. this entry must equal half of the address value where the string starts or 0x00 if the string does not exist. 0x53 0x1f iproduct index to product string. this entry must equal half of the address value where the string starts or 0x00 if the string does not exist. 0x69 0x20 iserialnumber index to serial number string. this entry must equal half of the address value where the string starts or 0x00 if the string does not exist. the usb mass storage class bulk-only transport specification requires a unique serial number (in upper case, hexadecimal characters) for each device. 0x75 0x21 bnumconfigurations number of configurations supported 1 for mass storage: 2 for hid: 3 for csm 0x03 device qualifier 0x22 blength length of device descriptor in bytes 0x0a 0x23 bdescriptor type descriptor type 0x06 0x24 bcdusb (lsb) usb specification release number in bcd 0x00 0x25 bcdusb (msb) usb specification release number in bcd 0x02 0x26 bdeviceclass device class 0x00 0x27 bdevicesubclass device subclass 0x00 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 28 of 44 0x28 bdeviceprotocol device protocol 0x00 0x29 bmaxpacketsize0 usb packet size supported for default pipe 0x40 0x2a bnumconfigurations number of configurations supported 0x01 0x2b breserved reserved for future use. must be set to zero 0x00 configuration descriptor 0x2c blength length of configurat ion descriptor in bytes 0x09 0x2d bdescriptortype descriptor type 0x02 0x2e btotallength (lsb) number of bytes return ed in this configuration. this includes the configuration descriptor plus all the interface and endpoint descriptors. 0x20 0x2f btotallength (msb) 0x00 0x30 bnuminterfaces number of interfaces supported 0x01 0x31 bconfiguration value the value to use as an argument to set configuration to select the configuration. this value must be set to 0x01. 0x01 0x32 iconfiguration index to the configurati on string. this entry must equal half of the address value where the string starts, or 0x00 if the string does not exist. 0x00 0x33 bmattributes device attrib utes for this configuration bit 7 reserved. must be set to ?1? bit 6 self powered. see table 4 on page 15 for reported value bit 5 remote wakeup. must be set to ?0? bits 4?0 reserved. must be set to ?0? 0xc0 0x34 bmaxpower maximum power consumpt ion for this configuration. units used are ma*2 (i.e., 0x31 = 98 ma, 0xf9 = 498 ma). the value entered here is only used by the 56-pin packages and affect the reported value of bi t 6 of address 0x33 in that case. see ta b l e 4 on page 15 for a description of what value is reported to the host by the at2lp. 0x01 interface and endpoint descriptors interface descriptor 0x35 blength length of interface descriptor in bytes 0x09 0x36 bdescriptortype descriptor type 0x04 0x37 binterfacenumber interface number 0x00 0x38 balternatesetting alternate setting 0x00 0x39 bnumendpoints number of endpoints 0x02 0x3a binterfaceclass interface class 0x08 0x3b binterfacesubclass interface subclass 0x06 0x3c binterfaceprotocol in terface protocol 0x50 0x3d iinterface index to first interface string. this entry must equal half of the address value where the string starts or 0x00 if the string does not exist. 0x00 usb bulk-out endpoint 0x3e blength length of this descriptor in bytes 0x07 0x3f bdescriptortype endpoint descriptor type 0x05 0x40 bendpointaddress this is an out endpoint, endpoint number 2. 0x02 0x41 bmattributes this is a bulk endpoint. 0x02 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 29 of 44 0x42 wmaxpacketsize (lsb) maximum data transfer size. to be set by speed (full speed 0x0040; high-speed 0x0200) 0x00 0x43 wmaxpacketsize (msb) 0x02 0x44 binterval high speed interval for polling (maximum nak rate) 0x00 usb bulk in endpoint 0x45 blength length of this descriptor in bytes 0x07 0x46 bdescriptortype endpoint descriptor type 0x05 0x47 bendpointaddress this is an in endpoint, endpoint number 6 0x86 0x48 bmattributes this is a bulk endpoint 0x02 0x49 wmaxpacketsize (lsb) maximum data transfer size. automatically set by at2 (full speed 0x0040; high-speed 0x0200) 0x00 0x4a wmaxpacketsize (msb) 0x02 0x4b binterval high speed interval for polling (maximum nak rate) 0x00 (optional) hid interface descriptor 0x4c blength length of hid interface descriptor 0x09 0x4d bdescriptortypes interface descriptor type 0x04 0x4e binterfacenumber number of interfaces (2) 0x02 0x4f balternatesetting alternate setting 0x00 0x50 bnumendpoints number of endpoints used by this interface 0x01 0x51 binterfaceclass class code 0x03 0x52 binterfacesubclass sub class 0x00 0x53 binterfacesubsubclass sub sub class 0x00 0x54 iinterface index of string descriptor 0x00 usb interrupt in endpoint 0x5e blength length of this descriptor in bytes 0x07 0x5f bdescriptortype endpoint descriptor type 0x05 0x60 bendpointaddress this is an in endpoint, endpoint number 1 0x81 0x61 bmattributes this is an interrupt endpoint 0x03 0x62 wmaxpacketsize (lsb) max data transfer size 0x02 0x63 wmaxpacketsize (msb) 0x00 0x64 binterval interval for polling (max nak rate) 0x10 (optional) hid descriptor 0x55 blength length of hid descriptor 0x09 0x56 bdescriptortype descriptor type hid 0x21 0x57 bcdhid (lsb) hid class specific ation release number (1.10) 0x10 0x58 bcdhid (msb) 0x01 0x59 bcountrycode country code 0x00 0x5a bnumdescriptors number of class descriptors (1 report descriptor) 0x01 0x5b bdescriptortype descriptor type 0x22 0x5c wdescriptorlength (lsb) length of hid report descriptor 0x22 0x5d wdescriptorlength (msb) 0x00 terminator descriptors 0x65 terminator 0x00 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 30 of 44 (optional) hid report descriptor 0x66 usage_page vendor defined 0x06 0x67 0xa0 0x68 0xff 0x69 usage vendor defined 0x09 0x6a 0xa5 0x6b collection application 0xa1 0x6c 0x01 0x6d usage vendor defined 0x09 0x6e 0xa6 input report 0x6f usage vendor defined 0x09 0x70 0xa7 0x71 logical_minimum ?128 0x15 0x72 0x80 0x73 logical_maximum 127 0x25 0x74 0x7f 0x75 report_size 8 bits 0x75 0x76 0x08 0x77 report_count 2 fields 0x95 0x78 0x02 0x79 input input (data, variable, absolute) 0x81 0x7a 0x02 output report 0x7b usage usage - vendor defined 0x09 0x7c 0xa9 0x7d logical_minimum logical minimum (?128) 0x15 0x7e 0x80 0x7f logical_maximum logical maximum (127) 0x25 0x80 0x7f 0x81 report_size report size 8 bits 0x75 0x82 0x08 0x83 report_count report count 2 fields 0x95 0x84 0x02 0x85 output output (data, variable, absolute) 0x91 0x86 0x02 0x87 end collection 0xc0 standard content security interface descriptor (optional) 0x88 blength byte length of this descriptor 0x09 0x89 bdescriptortype interface descriptor type 0x0d 0x8a binterfacenumber number of interface 0x02 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 31 of 44 0x8b balternatesetting value used to select an alternate setting for the interface identified in prior field 0x00 0x8c bnumendpoints number of endpoints used by this interface (excluding endpoint 0) that are csm dependent 0x02 0x8d binterfaceclass 0x0d 0x8e binterfacesubclass must be set to zero 0x00 0x8f binterfaceprotocol mu st be set to zero 0x00 0x90 iinterface index of a string descrip tor that describes this interface 0x00 channel descriptor 0x91 blength length of this descriptor in bytes 0x09 0x92 bdescriptortype channel descriptor type 0x22 0x93 bchannelid number of the channel mu st be a zero-based value that is unique across the device 0x00 0x94 bmattributes bits7:5 reserved. must be set to zero 0x01 bits 4:0 0x95 brecipient identifier of the target recipient if recipient type field of bmattributes = 1 then brecipient field is the binterfacenumber if recipient type field of bmattributes = 2 then brecipient field is an endpoint address, where: d7: direction (0 = out, 1 = in) d6...d4: reserved and set to zero d3...d0: endpoint number 0x00 0x96 brecipientalt alternate setting for the interface to which this channel applies 0x00 0x97 brecipientlogicalunit recipient logical unit 0x00 0x98 bmethod index of a class-specific csm descriptor that describes one of the content security methods (csm) offered by the device 0x01 0x99 bmethodvariant csm variant descriptor 0x00 csm descriptor 0x9a blength byte length of this descriptor 0x06 0x9b bdescriptortype csm descriptor type 0x23 0x9c bmethodid index of a class-specif ic csm descriptor that describes on of the content security methods offered by the device 0x01 0x9d icsmdescriptor index of string descript or that describes the content security method 0x00 0x9e bcdversion (lsb) csm descriptor version number 0x10 0x9f bcsversion (msb) 0x02 0xa0 terminator 0x00 usb string descripto r?index 0 (langid) 0xa1 blength langid string descriptor length in bytes 0x04 0xa2 bdescriptortype descriptor type 0x03 0xa3 langid (lsb) language supported. the cy7c68300b supports one langid value. 0x09 0xa4 langid (msb) 0x04 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 32 of 44 usb string descriptor?manufacturer 0xa5 blength string descriptor length in bytes (including blength) 0x2c 0xa6 bdescriptortype descriptor type 0x03 0xa7 bstring unicode character lsb ?c? 0x43 0xa8 bstring unicode character msb 0x00 0xa9 bstring unicode character lsb ?y? 0x79 0xaa bstring unicode character msb 0x00 0xab bstring unicode character lsb ?p? 0x70 0xac bstring unicode character msb 0x00 0xad bstring unicode character lsb ?r? 0x72 0xae bstring unicode character msb 0x00 0xaf bstring unicode character lsb ?e? 0x65 0xb0 bstring unicode character msb 0x00 0xb1 bstring unicode character lsb ?s? 0x73 0xb2 bstring unicode character msb 0x00 0xb3 bstring unicode character lsb ?s? 0x73 0xb4 bstring unicode character msb 0x00 0xb5 bstring unicode character lsb ? ? 0x20 0xb6 bstring unicode character msb 0x00 0xb7 bstring unicode character lsb ?s? 0x53 0xb8 bstring unicode character msb 0x00 0xb9 bstring unicode character lsb ?e? 0x65 0xba bstring unicode character msb 0x00 0xbb bstring unicode character lsb ?m? 0x6d 0xbc bstring unicode character msb 0x00 0xbd bstring unicode character lsb ?i? 0x69 0xbe bstring unicode character msb 0x00 0xbf bstring unicode character lsb ?c? 0x63 0xc0 bstring unicode character msb 0x00 0xc1 bstring unicode character lsb ?o? 0x6f 0xc2 bstring unicode character msb 0x00 0xc3 bstring unicode character lsb ?n? 0x6e 0xc4 bstring unicode character msb 0x00 0xc5 bstring unicode character lsb ?d? 0x64 0xc6 bstring unicode character msb 0x00 0xc7 bstring unicode character lsb ?u? 0x75 0xc8 bstring unicode character msb 0x00 0xc9 bstring unicode character lsb ?c? 0x63 0xca bstring unicode character msb 0x00 0xcb bstring unicode character lsb ?t? 0x74 0xcc bstring unicode character msb 0x00 0xcd bstring unicode character lsb ?o? 0x6f table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 33 of 44 0xce bstring unicode character msb 0x00 0xcf bstring unicode character lsb ?r? 0x72 0xd0 bstring unicode character msb 0x00 usb string descriptor?product 0xd1 blength string descriptor length in bytes (including blength) 0x2c 0xd2 bdescriptortype descriptor type. 0x03 0xd3 bstring unicode character lsb ?u? 0x55 0xd4 bstring unicode character msb 0x00 0xd5 bstring unicode character lsb ?s? 0x53 0xd6 bstring unicode character msb 0x00 0xd7 bstring unicode character lsb ?b? 0x42 0xd8 bstring unicode character msb 0x00 0xd9 bstring unicode character lsb ?2? 0x32 0xda bstring unicode character msb 0x00 0xdb bstring unicode character lsb ?.? 0x2e 0xdc bstring unicode character msb 0x00 0xdd bstring unicode character lsb ?0? 0x30 0xde bstring unicode character msb 0x00 0xdf bstring unicode character lsb ? ? 0x20 0xe0 bstring unicode character msb 0x00 0xe1 bstring unicode character lsb ?d? 0x53 0xe2 bstring unicode character msb 0x00 0xe3 bstring unicode character lsb ?i? 0x74 0xe4 bstring unicode character msb 0x00 0xe5 bstring unicode character lsb ?s? 0x6f 0xe6 bstring unicode character msb 0x00 0xe7 bstring unicode character lsb ?k? 0x72 0xe8 bstring unicode character msb 0x00 usb string descriptor?serial number ( note the usb mass storage class specification requires a unique serial number in each device. if you do not provide a unique serial number, the operating system may cr ash. the serial numbe r must be at least 12 characters, but some usb hosts only use the least significant 12 characters of the serial number as a unique identifier. 0xe9 blength string descriptor length in bytes (including blength). 0x22 0xea bdescriptor type descriptor type. 0x03 0xeb bstring unicode character lsb ?1? 0x31 0xec bstring unicode character msb 0x00 0xed bstring unicode character lsb ?2? 0x32 0xee bstring unicode character msb 0x00 0xef bstring unicode character lsb ?3? 0x33 0xf0 bstring unicode character msb 0x00 0xf1 bstring unicode character lsb ?4? 0x34 0xf2 bstring unicode character msb 0x00 0xf3 bstring unicode character lsb ?5? 0x35 0xf4 bstring unicode character msb 0x00 table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 34 of 44 note more than 0x100 bytes of configuration are shown for exam ple only. the at2lp only supports addresses up to 0xff. 0xf5 bstring unicode character lsb ?6? 0x36 0xf6 bstring unicode character msb 0x00 0xf7 bstring unicode character lsb ?7? 0x37 0xf8 bstring unicode character msb 0x00 0xf9 bstring unicode character lsb ?8? 0x38 0xfa bstring unicode character msb 0x00 0xfb bstring unicode character lsb ?9? 0x39 0xfc bstring unicode character msb 0x00 0xfd bstring unicode character lsb ?0? 0x30 0xfe bstring unicode character msb 0x00 0xff bstring unicode character lsb ?a? 0x41 0xxx bstring unicode character msb 0x00 0xxx bstring unicode character lsb ?b? 0x42 0xxx bstring unicode character msb 0x00 identify device string ( note this is not a unicode string. it is the ascii stri ng returned by the device in the identify device information. it is a fixed length (24 bytes). changing this string may cause cd authoring software to incorrectly identify the device.) 0xxx device name byte 1 ascii character ?c? 0x43 0xxx device name byte 2 ascii character ?y? 0x79 0xxx device name byte 3 ascii character ?p? 0x70 0xxx device name byte 4 ascii character ?r? 0x72 0xxx device name byte 5 ascii character ?e? 0x65 0xxx device name byte 6 ascii character ?s? 0x73 0xxx device name byte 7 ascii character ?s? 0x73 0xxx device name byte 8 ascii character ? ? 0x20 0xxx device name byte 9 ascii character ?c? 0x43 0xxx device name byte 10 ascii character ?u? 0x75 0xxx device name byte 11 ascii character ?s? 0x73 0xxx device name byte 12 ascii character ?t? 0x74 0xxx device name byte 13 ascii character ?o? 0x6f 0xxx device name byte 14 ascii character ?m? 0x6d 0xxx device name byte 15 ascii character ? ? 0x20 0xxx device name byte 16 ascii character ?n? 0x4e 0xxx device name byte 17 ascii character ?a? 0x61 0xxx device name byte 18 ascii character ?m? 0x6d 0xxx device name byte 19 ascii character ?e? 0x65 0xxx device name byte 20 ascii character ? ? 0x20 0xxx device name byte 21 ascii character ?l? 0x4c 0xxx device name byte 22 ascii character ?u? 0x55 0xxx device name byte 23 ascii character ?n? 0x4e 0xxx device name byte 24 ascii character ?0? 0x30 0xxx unused rom space amount of unused ro m space varies depending on strings. 0xff table 11. configuration data organization (continued) byte address configuration item name configuration item description required contents variable contents [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 35 of 44 programming the eeprom there are three methods of programming the eeprom: stand-alone eeprom programmer vendor-specific usb commands, listed in ta b l e 1 2 in-system programming (for ex ample, bed-of- nails tester) any vendor-specific usb write request to the serial rom device configuration space simultaneousl y update internal configuration register values as well. if the i 2 c device is programmed without vendor specific usb commands, the at2lp must be synchronously reset (toggle reset#) before configuration data is reloaded. the at2lp supports a subset of the ?slow mode? specification (100 khz) required for 24lcxxb eeprom family device support. features such as ?multi-master?, ?clock synchronization? (the scl pin is output only), ?10-bit addressing?, and ?cbus device support? are not supported. vendor-specific usb commands enable the at2lp to address up to 256 bytes of eeprom data. load_config_data this request enables writes to the at2lp?s configuration data space. the windex field specifie s the starting address and the wlength field denotes the data length in bytes. legal values for wvalue are as follows: 0x0000 internal config bytes, address range 0x2 ? 0xf 0x0002 external i 2 c memory device internal config byte writes must be constrained to addresses 0x2 through 0xf, as shown in table 12 . attempts to write outside this address space result in undefined operation. internal config byte writes only overwrite at2lp conf iguration byte registers, the original data source (i 2 c memory device) remains unchanged. read_config_data this usb request enables data retrieval from the data source specif ied by the wvalue field. data is retrieved beginning at the address specified by the windex field (see ta b l e 1 2 ). the wlength field denotes the length in byte s of data requested from the data source. legal values for wvalue are as follows: 0x0000 configuration bytes, addresses 0x0 ? 0xf only 0x0002 external i 2 c memory device illegal values for wvalue result in an und efined operation. attempted reads from an i 2 c memory device when none is connected result in an undefined operation. attempts to read configuration bytes with starting addresse s greater than 0xf also, result in an und efined operation. table 12. eeprom-related vendor-specific commands label bmrequesttype brequest wvalue windex wlength data load_config_data 0x40 0x01 0x0000 30x02 ? 0x0f data length configuration data read_config_data 0xc0 0x02 data source starting address data length configuration data [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 36 of 44 absolute maximum ratings exceeding maximum ratings may impair the useful life of the device. these user guidelines are not tested. storage temperature ..... ............ ............... ?65 ? c to +150 ? c ambient temperature with power applied commercial .................................................... 0 ? c to +70 ? c automotive.................................................. ?40 ? c to +85 ? c supply voltage to ground potentia l..............?0.5 v to +4.0 v dc input voltage to any input pin ............................... 5.25 v dc voltage applied to outputs in high z state ..................................... ?0.5 v to v cc + 0.5 v power dissipation...................... ............................... 300 mw static discharge voltage.......................................... > 2000 v max output current per i/o port (d0-d7, d8-15, ata control)........................................ 10 ma operating conditions t a (ambient temperature under bias) commercial .................................................... 0 ? c to +70 ? c automotive.................................................. ?40 ? c to +85 ? c supply voltage..........................................+3.00 v to +3.60 v ground voltage................................................................. 0 v f osc (oscillator or crystal frequency) .... 24 mhz 100 ppm, parallel resonant dc characteristics parameter description conditions min typ max unit v cc supply voltage 3.00 3.3 3.60 v v cc ramp supply ramp up 0 v to 3.3 v 200 ? s v ih input high voltage 2 5.25 v v il input low voltage ?0.5 0.8 v i i input leakage current 0 < v ih < v cc 10 ? a v ih_x crystal input high voltage 2 5.25 v v il_x crystal input low voltage ?0.5 0.8 v v oh output voltage high i out = 4 ma 2.4 v v ol output voltage low i out = ?4 ma 0.4 v i oh output current high 4ma i ol output current low 4ma c in input pin capacitance all but dplus/dminus 10 pf dplus/dminus 15 pf i susp suspend current connected 0.5 1.2 ma cy7c68300c/cy7c68320c disconnected 0.3 1.0 ma suspend current connected 300 380 ? a cy7c68301c/cy7c68321c disconnected 100 150 ? a i cc supply current usb high speed 50 85 ma usb full speed 35 65 ma i unconfig unconfigured current current bef ore device is granted full amount requested in bmaxpower 43 ma t reset reset time after valid power v cc > 3.0 v 5.0 ms pin reset after power up 200 ? s [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 37 of 44 ac electrical characteristics ata timing characteristics the ata interface supports ata pio modes 0, 3, and 4, ultra dma modes 2, 3, and 4, and mu ltiword dma mode 2, according to the ata/atapi 6 specification. the highest enabled transfer rate common to both the at2lp and the attached mass storage device is used. the at2lp automatically determines the transfer rates during drive initialization based upon the values in the at2lp configuration space and t he data reported by the drives in response to an identify device command. usb transceiver characteristics complies with the usb 2.0 specif ication for full- and high speed modes of operation. ordering information ordering code definitions part number package type gpio pins cy7c68300c-56pvxc 56 ssop pb-free fo r self and bus powered designs ? CY7C68300C-56LTXC 56 qfn sawn pb-free for self and bus powered designs ? cy7c68301c-56ltxc 56 qfn sawn pb-free for battery powered designs ? cy7c68320c-56ltxc 56 qfn sawn pb-free for self and bus powered designs 3 [10] cy7c68321c-56ltxc 56 qfn sawn pb-free for battery powered designs 3 [10] cy7c68320c-100axc 100 tqfp pb-free for self and bus powered designs 6 cy7c68321c-100axc 100 tqfp pb-fre e for battery powered designs 6 cy7c68320c-100axa 100 tqfp pb-free for self and bus powered designs (automotive grade) 6 cy4615b ez-usb at2lp reference design kit n/a note 10. the general purpose inputs can be enabled on atapuen, pwr500#, and drvpwrvld with eeprom byte 8, bit 7 on cy7c68320c/cy7c683 21c. temperature range: x = c or a; c = commercial; a = automotive grade x = pb-free package type: xxxx = 56pv or 56lt or 100a; 56pv = 56-pin ssop; 56lt = 56-pin qfn; 100a =100-pin tqfp part identifier company id: cy = cypress cy 7c683xxc - xxxx x x [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 38 of 44 package diagrams figure 11. 100-pin thin plastic qu ad flatpack (14 20 1.4 mm) a101 51-85050 *c [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 39 of 44 figure 12. 56-pin shrunk small outline package 056 figure 13. 56-pin qfn 8 8 mm lf56a 51-85062 *d 51-85144 *h 0.20[0.008] r. top view 0.80[0.031] 7.70[0.303] 7.90[0.311] a c 1.00[0.039] max. n bottom view seating plane n 2 0.18[0.007] 0.50[0.020] 1 1 0.08[0.003] 0.50[0.020] 0.05[0.002] max. 2 side view (4x) c 0.24[0.009] 0.20[0.008] ref. 0.80[0.031] max. pin1 id 0-12 6.45[0.254] 8.10[0.319] 7.80[0.307] 6.55[0.258] 0.45[0.018] 8.10[0.319] 7.90[0.311] 7.80[0.307] 7.70[0.303] dia. 0.28[0.011] 0.30[0.012] 6.55[0.258] 6.45[0.254] 0.60[0.024] 1. hatch area is solderable exposed metal. 2. reference jedec#: mo-220 4. all dimensions are in mm [min/max] notes : part # pb-free standard ly56 5. package code description 3. package weight: 0.162g lf56 solderable exposed pad 6.1 6.1 [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 40 of 44 figure 14. 56-pin qfn (8 8 0.9 mm) - sawn general pcb layout recommendations for usb mass storage designs the following recommendations must be followed to ensure reliable high performance operation: use at least a four-layer, impedance controlled board to maintain signal quality. specify specific impedance ta rgets (ask your board vendor what they can achieve). maintain uniform trace widths and trace spacing to control impedance. minimize reflected signals by avoiding using stubs and vias. connect the usb connector shell and signal ground as near to the usb connector as possible. use bypass or flyback capacito rs on vbus near the connector. keep dplus and dminus trace lengths to within 2 mm of each other in length, with a pref erred length of 20 to 30 mm. maintain a solid ground plane under the dplus and dminus traces. do not allow the plane to be split under these traces. do not place vias on the dplus or dminus trace routing for a more stable design. isolate the dplus and dminus traces from all other signal traces by no less than 10 mm. source for recommendations: ez-usb fx2lp pcb design recommendations www.cypress.com/?docid=4696 high-speed usb platform design guidelines http://www.usb.org/develope rs/docs/hs_usb_pdg_r1_0.pdf quad flat package no leads (qfn) package design notes electrical contact of the part to the printed circuit board (pcb) is made by soldering the leads on the bottom surface of the package to the pcb. hence, spec ial attention is required to the heat transfer area below the pa ckage to provide a good thermal bond to the circuit board. a copper (cu) fill must be designed into the pcb as a thermal pad under the package. heat is transferred from the at2lp through the device?s metal paddle on the bottom side of the package. heat from here is conducted to the pcb at the thermal pad. it is then conducted from the thermal pad to the pcb inner ground plane by a 5 5 array of vias. a via is a plated through-hole in t he pcb with a finished diameter of 13 mil. the qfn?s metal die paddle must be soldered to the pcb?s thermal pad. solder mask is placed on the board top side over each via to resist solder flow into the via. the mask on the top side also minimizes outgassing during the solder reflow process. 001-53450 *b [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 41 of 44 for further information on this package design, refer to the application note surface mount assembly of amkor?s microleadframe (mlf) technology . the application note provides detailed information on board mounting guidelines, soldering flow, rework process, and so on. figure 15 displays a cross-sectional area underneath the package. the cross section is of only one via. the solder paste template needs to be designed to enable at least 50% solder coverage. the thickness of the solder paste template must be 5 mil. it is recommended that ?no clean,? type 3 solder paste is used to mount the part. nitrogen purge is recommended during reflow. figure 15. cross-section of the area under the qfn package figure 16 is a plot of solder mask pattern and figure 17 displays an x-ray image of assembly (darker areas indicate solder). figure 16. plot of the solder mask (white area) figure 17. x-ray image of the assembly other design considerations certain design considerations must be followed to ensure proper operation of the cy7c68300c/cy7c68301c. the following items must be taken into account when designing a usb device with the cy7c68300c/cy7c68301c. proper power up sequence power must be applied to the cy7c68300c/cy7c68301c before, or at the same time as the ata/atapi device. if power is supplied to the drive first, the cy7c68300c/cy7c68301c startup in an undefined state. designs that use separate power supplies for the cy7c68300c/cy7c68301c and the ata/atapi device are not recommended. ide removable media devices the at2lp does not fully support ide removable media devices. changes in media state are not reported to the operating system so users are unable to eject or reinsert media properly. this may result in lost or corrupted data. note that standard atapi optical drives and ata compactflash-typ e devices are not part of this group. devices with small buffers the size of the drive?s buffer ca n greatly affect the overall data transfer performance. ensure that drives have large enough buffers to handle the flow of data to and from it. the exact buffer size needed depends on a number of variables, but a good rule of thumb to follow is: (approx min buffer) = (data rate) * (seek time + rotation time + other) where ?other? may include things such as the time required to switch heads and power up a laser. drives with buffers that are too small to handle the extra data may perform considerably slower than expected. 0.017? dia solder mask cu fill cu fill pcb material pcb material 0.013? dia via hole for thermally connecting the qfn to the circuit board ground plane. this figure only shows the top three layers of the circuit board: top solder, pcb dielectric, and the ground plane [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 42 of 44 acronyms document conventions units of measure acronym description eeprom electrically erasable programmable read-only memory i/o input/output lsb least significant bit msb most significant bit pcb printed circuit board qfn quad flat no leads ssop shrink small-outline package tqfp thin quad flat pack usb universal serial bus symbol unit of measure ns nano seconds vvolts mv milli volts w micro watts a micro amperes ma milli amperes s micro seconds ms milli seconds mhz mega hertz f micro farad pf pico farad mw milli watts wwatts ppm parts per million c degree celcius [+] feedback
cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c document number: 001-05809 rev. *h page 43 of 44 document history page description title: cy7c68300c/cy7c68301c/cy7c68320c/cy7 c68321c ez-usb at2lp? usb 2.0 to ata/atapi bridge document number: 001-05809 rev. ecn no. submission date orig. of change description of change ** 409321 see ecn gir new data sheet. *a 611658 see ecn ari/kku implemented new template . added part number cy7c68301c-56pvxc to the ordering information. corrected part numbers on figure 5 and 6. moved figure titles to the top of each figure pe r new template requirements. made grammatical corrections. changed the fused memory data section. added new figure: 56-pin ssop (cy7c68320c/cy7c68321c). changed figure 10 to reflect actual flow for operational mode. changes made between ?vbus_ata_enable pin high?? and ?board manufacturing test mode?. formatted ?0=?, ?1=? lines in configuration data organization to always show up in the same order. re-worded 3rd bullet point in the operation selection flow section. gpio2_nhs function removed and corrected the sense of ata_en to allow drive on ?0? and high-z on ?1?. *b 2717536 06/11/2009 dpt added 56 qfn (8 x 8 mm) package diagram and added CY7C68300C-56LTXC, cy7c68301c-56ltxc, cy7c68320c-56ltxc, and cy7c68321c-56ltxc parts in the ordering information table *c 2733311 07/08/09 nmma updated package drawing spec 51-85062 updated link in the additional resources section updated ordering information table *d 2755364 08/28/09 vivg updated information on automotive parts in features, absolute maximum ratings, and ordering information sections *e 2813871 11/25/09 vivg/pyrs deleted note 1. added contents page *f 2896245 03/19/10 vrd updated ordering information and package diagrams. *g 2956403 06/19/10 nmma updated ordering information. *h 3124965 01/03/2011 nmma updated pin diagrams . updated ordering information . added ordering code definitions . added acronyms and units of measure . updated in new template. [+] feedback
document number: 001-05809 rev. *h revised january 3, 2011 page 44 of 44 all products and company names mentioned in this document may be the trademarks of their respective holders. cy7c68300c, cy7c68301c cy7c68320c, cy7c68321c ? cypress semiconductor corporation, 2006-2011. the information contained herein is subject to change without notice. cypress s emiconductor corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a cypress product. nor does it convey or imply any license under patent or other rights. cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement wi th cypress. furthermore, cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. any source code (software and/or firmware) is owned by cypress semiconductor corporation (cypress) and is protected by and subj ect to worldwide patent protection (united states and foreign), united states copyright laws and internatio nal treaty provisions. cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of, and compile the cypress source code and derivative works for the sole purpose of creating custom software and or firmware in su pport of licensee product to be used only in conjunction with a cypress integrated circuit as specified in the applicable agreement. any reproduction, modification, translation, compilation, or repre sentation of this source code except as specified above is prohibited without the express written permission of cypress. disclaimer: cypress makes no warranty of any kind, express or implied, with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. cypress reserves the right to make changes without further notice to t he materials described herein. cypress does not assume any liability arising out of the application or use of any product or circuit described herein. cypress does not authori ze its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress? prod uct in a life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. use may be limited by and subject to the applicable cypress software license agreement. sales, solutions, and legal information worldwide sales and design support cypress maintains a worldwide network of offices, solution center s, manufacturers representatives, and distributors. to find th e office closest to you, visit us at cypress.com/sales. products automotive cypress.co m/go/automotive clocks & buffers cypress.com/go/clocks interface cypress. com/go/interface lighting & power control cypress.com/go/powerpsoc cypress.com/go/plc memory cypress.com/go/memory optical & image sensing cypress.com/go/image psoc cypress.com/go/psoc touch sensing cyp ress.com/go/touch usb controllers cypress.com/go/usb wireless/rf cypress.com/go/wireless psoc solutions psoc.cypress.com/solutions psoc 1 | psoc 3 | psoc 5 [+] feedback

▲Up To Search▲

Price & Availability of CY7C68300C-56LTXC

	To Download CY7C68300C-56LTXC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .